Include binarybuilds from dependencies. #52
Conversation
|
Quote from @staticfloat on Slack regarding JuliaPackaging/BinaryBuilder.jl#194:
|
|
Ah ok, good to know. So then I guess we have to make sure that these build files don't clash with the ones in the other packages if we want to be able to use them together right? |
|
We could put back the packages (LibGEOS, Proj4, CodecZlib) in However, as before, clashes can still occur due to other packages or system libraries. |
|
The files are being installed in a GDAL-specific location, so no clashing
will occur. If another package that Julia has already using’ed also
requires libGEOS, then that library will already be loaded into Julia’s
address space, and libGDAL won’t need to load it. That should all work as
long as compatible versions are all available.
-E
On Sat, Jul 7, 2018 at 04:29 Maarten Pronk ***@***.***> wrote:
We could put back the packages (LibGEOS, Proj4, CodecZlib) in REQUIRE, in
this way you guarantee that there won't be version differences if one of
those package is loaded first.
However, as before, clashes can still occur due to other packages or
system libraries.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#52 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAH_aOSFwWGtFZAUrILDLwWEYBm1bWcwks5uEJuqgaJpZM4VGT9K>
.
--
…-E
|
For zlib this does not use the modified build.jl in the CodecZlib repo, but the original bicycle1885/ZlibBuilder version. We don't support the other platforms yet anyway. If we run into issues like JuliaIO/CodecZlib.jl#21, perhaps we should use an older build.
and a warning for eval
This is the recommended work-around approach untill JuliaPackaging/BinaryBuilder.jl#194 is done.
See also https://github.com/JuliaIO/ImageMagick.jl/tree/sd/binaryprovider/deps
Depencies are
build.jlfiles from their latest releases.